Committed to connecting the world

  •  
wtisd

ITU-T work programme

Home : ITU-T Home : ITU-T Work Programme : X.1205     
  ITU-T A.5 justification information for referenced document IETF RFC 1661 (1994) in draft X.1205
1. Clear description of the referenced document:
Name: IETF RFC 1661 (1994)
Title: The Point-to-Point Protocol (PPP), W. Simpson, July 1994.
2. Status of approval:
Normative
3. Justification for the specific reference:
Draft Rec. X.cso refers to The Point-to-Point Protocol (PPP), IETF RFC 1661, July 1999.
4. Current information, if any, about IPR issues:
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=1661
5. Other useful information describing the "Quality" of the document:
This RFC has been in existence since July 1994.
6. The degree of stability or maturity of the document:
RFC 1661 is now an approved standard, STD0051.
7. Relationship with other existing or emerging documents:
RFC 1661 describing PPP is a basis to a suite of documents describing PPP framing, PPP link and network protocols (e.g. RFC 1662, 1332, 1334).
8. Any explicit references within that referenced document should also be listed:
[1] Perkins, D., "Requirements for an Internet Standard Point-to-/
Point Protocol", RFC 1547, Carnegie Mellon University,/
December 1993./
/
[2] Reynolds, J., and Postel, J., "Assigned Numbers", STD 2, RFC/
1340, USC/Information Sciences Institute, July 1992.
9. Qualification of ISOC/IETF:
9.1-9.6     Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7     The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8     Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
10. Other (for any supplementary information):
If the Study Group decides to make the reference to the RFC, the reference should always be made by RFC number (and not by other designations such as STD, BCP, etc.). References should not be made to documents referred to as "Internet Drafts" or RFCs categorized as "Historic".
Note: This form is based on Recommendation ITU-T A.5